Personalized automatic teller machine

ABSTRACT

Computer implemented systems and methods are provided for an automatic teller machine. In some embodiments, an automatic teller machine may comprise a touch-sensitive display, one or more memory devices storing instructions, and one or more processors. The one or more processors may be configured to receive authentication data associated with a user, retrieve user profile information based on the authentication data, determine user interface attributes based on the user profile information; and generate an automatic teller machine interface based on the user profile information.

PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No.15/892,392, filed on Feb. 8, 2018, which is a continuation of U.S.patent application Ser. No. 15/389,313, filed on Dec. 22, 2016, whichclaims priority under 35 U.S.C. § 119 to U.S. Provisional ApplicationNo. 62/387 194, filed on Dec. 24, 2015, and entitled “PersonalizedAutomatic Teller Machine.” The disclosures of the above-referencedapplications are expressly incorporated herein by reference in theirentireties.

TECHNICAL FIELD

The disclosed embodiments generally relate to improvements to automaticteller machines, and particularly, to improvements to automatic tellermachines through hardware and software embodiments facilitatingautomatic teller machine personalization.

BACKGROUND

The ubiquity of automatic teller machines, or ATMs, has increasedsubstantially in recent decades. While greater availability and improvedfeatures have made ATMs more useful in certain ways, numerouslimitations in ATM design have remained. Often ATMs are more difficultfor some users to operate than for others. For example, ATMs ofteninclude a display that can only be viewed from a limited range ofviewing angles and lines of sight. This may make operation of the ATMdifficult or uncomfortable particularly for users outside of the nominalheight range for viewing the ATM display that must strain to operate themachine.

Further, many aspects of ATM design are often fixed and unchangeablewhen an ATM is in service. Examples include display location buttonlocation, button size, hardware for accepting transaction cards orcurrency, language, color combination, and placement of signs andinstructions. Such aspects may be configured optimally for some users,but due to their fixed nature may render ATM use inconvenient orimpossible for other users.

Further, the attachment of unauthorized devices to ATMs by thieves is agrowing problem due to the increasing complexity of ATM designsproviding numerous locations for attaching such devices. Such devicescan be difficult and expensive to detect, and if undetected, may reducethe effectiveness or negate entirely ATM features intended to protectusers from fraud or theft.

In view of the shortcomings of current. ATM systems, improved ATMdesigns are desired.

SUMMARY

Disclosed embodiments provide methods and systems for proved ATMinterfaces. Disclosed embodiments improve upon disadvantages ofconventional ATM technologies, for example by providing personalizationand/or configurability, allowing an ATM to adapt to various users'physical characteristics, abilities, and/or preferences. Accordingly,where traditional ATMs may be more convenient or user friendly forcertain users, and less so for others, disclosed embodiments provideimproved functionality and ease of use across a wider variety of usersby customizing the ATM to individual users.

Such personalization may improve ergonomic properties of the ATM,improve speed and/or accuracy of user interactions with the ATM, and/orreduce inefficiency attributable to inaccurate user interaction with theATM. Personalization may also improve accessibility for users withdisabilities. Other improvements will also be apparent to those skilledin the art.

Consistent with a disclosed embodiment, an automatic teller machine isprovided. The automatic teller machine may include a touch-sensitivedisplay, one or more memory devices storing instructions, and one ormore processors. The one or more processors may be configured to executethe instructions to perform operations. The operations may includereceiving, from a user device, authentication data associated with auser. The operations may also include retrieving, over a network, userprofile information based on the authentication data determine userinterface attributes based on the user profile information. Theoperations may also include generating an automatic teller machineinterface based on the user profile information.

Consistent with another disclosed embodiment, a computer-implementedmethod for displaying an ATM interface is provided. The method maycomprise receiving, from a user device, authentication data associatedwith a user. The method may also include retrieving, over a network,user profile information based on the authentication data determininguser interface attributes based on the user profile information. Themethod may further include generating an automatic teller machineinterface based on the user profile information.

Consistent with other disclosed embodiments, non-transitorycomputer-readable storage media may store program instructions, whichare executed by at least one processor device and perform any of themethods described herein.

The foregoing general description and the following detailed descriptionare exemplary and explanatory only and are not restrictive of theclaims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate several embodiments and, togetherwith the description, serve to explain the disclosed principles. In thedrawings:

FIG. 1 is a diagram of an exemplary system, consistent with disclosedembodiments;

FIG. 2 is a diagram of an exemplary computer system, consistent withdisclosed embodiments;

FIG. 3 is a flowchart of an exemplary process for ATM personalization,consistent with disclosed embodiments;

FIG. 4 is a diagram of a portion of an exemplary ATM interface,consistent with disclosed embodiments;

FIG. 5 is a cross sectional diagram of an ATM display, consistent withdisclosed embodiments;

FIGS. 6A, 6B, 7A, 7B, 8A, and 8B are examples of ATM interfaces,consistent with disclosed embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to exemplary embodiments, examplesof which are illustrated in the accompanying drawings and disclosedherein. Wherever convenient, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

FIG. 1 shows a diagram of an exemplary system 100, consistent withdisclosed embodiments. As shown in FIG. 1, system 100 may include afinancial service provider device 102, a local financial serviceprovider device 104, a user device 106, a personalization database 110,and a network 112 to facilitate communication among the components ofsystem 100. The components and arrangement of the components included insystem 100 may vary. Thus, system 100 may further include othercomponents that perform or assist in the performance of one or moreprocesses consistent with the disclosed embodiments. The components andarrangements shown in FIG. 1 are not intended to limit the disclosedembodiments, as the components used to implement the disclosed processesand features may vary.

In accordance with disclosed embodiments, system 100 may include afinancial service provider (FSP) device 102. FSP device 102 may be asystem associated with a financial service provider (not shown), such asa bank, a credit card company, a lender, brokerage firm, or any othertype of financial service entity that generates, provides, manages,maintains financial service accounts, etc. for one or more users. FSPdevice 102 may be one or more computing systems that are configured toexecute software instructions stored on one or more memory devices toperform one or more operations consistent with the disclosedembodiments. For example, FSP device 102 may include one or more memorydevice(s) storing data and software instructions and one or moreprocessor(s) configured to use the data and execute the softwareinstructions to perform server-based functions and operations known tothose skilled in the art. FSP device 102 may include one or more generalpurpose computers, mainframe computers, or any combination of thesetypes of components.

In certain embodiments, FSP device 102 may be configured as a particularapparatus, system, and the like based on the storage, execution, and/orimplementation of the software instructions that perform one or moreoperations consistent with the disclosed embodiments. FSP device 102 maybe standalone, or it may be part of a subsystem, which may be part of alarger system. For example, FSP device 102 may represent distributedservers that are remotely located and communicate over a network (e.g.,network 112) or a dedicated network, such as a LAN, for a financialservice provider. An exemplary computing system consistent with FSPdevice 102 is discussed in additional detail with respect to FIG. 2,below.

FSP device 102 may include or may access one or more storage devicesconfigured to store data and/or software instructions used by one ormore processors of FSP device 102 to perform operations consistent withdisclosed embodiments. For example, FSP device 102 may include memory230 configured to store one or more software programs that performsseveral functions when executed by a processor. The disclosedembodiments are not limited to separate programs or computers configuredto perform dedicated tasks. For example, FSP device 102 may includememory that stores a single program or multiple programs. Additionally,FSP device 102 may execute one or more programs located remotely fromFSP device 102. For example, FSP device 102 may access one or moreremote programs stored in memory included with a remote component that,when executed, perform operations consistent with the disclosedembodiments. In certain aspects, FSP device 102 may include serversoftware that generates, maintains, and provides services associatedwith financial account management. In other aspects, FSP device 102 mayconnect separate server(s) or similar computing devices that generate,maintain, and provide services associated with financial data for afinancial service provider associated with FSP device 102.

System 100 may also include one or more local FSP devices 104. Local FSPdevices may include, for example, Automatic Teller Machines (“ATMs”) ordetection devices in local FSP branches or other locations (e.g., retaillocations, gas stations, etc.). Local FSP device 104 may include one ormore memory device(s) that store data that may be used for performingone or more processes consistent with the disclosed embodiments. Incertain aspects, local FSP device 104 may additionally, oralternatively, include one or more computer devices. For example, localFSP device 104 may include one or more memory device(s) storing data andsoftware instructions and one or more processor(s) configured to use thedata and execute the software instructions to perform computingfunctions and operations known to those skilled in the art.

Local FSP device 104 may further include computer device(s) that areconfigured to execute stored software instructions to perform operationsassociated with collecting, storing, and accessing biometric data,including one or more processes associated with gathering biometric datafrom a variety of sources, compiling the data, and organizing the datainto easily accessible profiles. Local FSP device 104 may include one ormore computer device(s) that may be a general purpose computer, server,mainframe computer, or any combination of these components. In certainembodiments, local FSP device 104 (or a system including local FSPdevice 104) may be configured as a particular apparatus, system, and thelike based on the storage, execution, and/or implementation of thesoftware instructions that perform one or more operations consistentwith the disclosed embodiments. A local FSP device 104 may bestandalone, or it may be part of a subsystem, which may be part of alarger system. For example, local FSP device 104 may representdistributed servers that are remotely located and communicate over anetwork (e.g., network 112) or a dedicated network, such as a LAN. Anexemplary computer system consistent with local FSP device 104 isdiscussed in additional detail with respect to FIG. 2. In certainembodiments, a third party may operate the components associated withlocal FSP device 104. Additionally or alternatively, local FSP device104 may be a part or subpart of FSP device 102.

System 100 may further include one or more user devices 106. A user 108may operate a user device 106, which may be a desktop computer, laptop,tablet, smartphone, multifunctional watch, pair of multifunctionalglasses, tracking device, chip-enabled payment card, or any suitabledevice with computing capability. User device 106 may include one ormore processor(s) and memory device(s) known to those skilled in theart. For example, user device 106 may include memory device(s) thatstore data and software instructions that, when executed by one or moreprocessor(s), perform operations consistent with the disclosedembodiments. In one aspect, user device 106 may have a financialapplication installed thereon, which may enable user device 106 tocommunicate with FSP device 102 and/or local FSP device 104 via network112. For instance, user device 106 may be a smartphone or tablet (or thelike) that executes a stored mobile application that performs onlinebanking operations. In other embodiments, user device 106 may connect toFSP device 102 and/or local FSP device 104 through use of browsersoftware stored and executed by user device 106. User device 106 may beconfigured to execute software instructions to allow a user to accessinformation stored in FSP device 102 such as, for example, financialinformation related to purchase transactions, financial statements,account information, rewards program information and the like.Additionally, user device 106 may be configured to execute softwareinstructions that initiate and conduct transactions with FSP device 102or local FSP device 104, such as, for example, ATM withdrawals, wiretransfers, debit card PIN resets, and call center transactions. Anexemplary computer system consistent with user device 106 is discussedin additional detail with respect to FIG. 2.

User 108 may operate user device 106 to perform one or more operationsconsistent with the disclosed embodiments. In one aspect, user 108 maybe a customer of a financial service provider associated with FSP device102. For instance, a financial service provider may maintain a financialservice account (e.g., checking account, savings account, debit cardaccount, or credit card account) for user 108 that the user may use topurchase goods and/or services. Additionally or alternatively, user 108may use user device 106 and the financial service account (for example,through a mobile application installed on user device 106) to withdrawcash from an ATM (such as local FSP device 104), contact a customer callcenter, transfer or wire money, or reset their debit account PIN.

User 108 may further operate user device 106 in order to be detected andrecognized by local FSP device 104. For example, user device 106 maydetect, through the user of network 112, a local FSP device 104 in itsimmediate proximity. Additionally or alternatively, local FSP device 104may detect user device 106 in its immediate proximity. User device 106may then connect to local FSP device 104 in order to initiate, conduct,or complete a financial transaction.

System 100 may also include one or more personalization databases 110.Personalization database 110 may include one or more memory device(s)that store data that may be used for performing one or more processesconsistent with the disclosed embodiment. In certain aspects,personalization database 110 may additionally, or alternatively, includeone or more servers or other type of computer devices. Thepersonalization database 110 server(s) may be one or more computingdevices configured to execute software instructions stored in memory toperform one or more processes consistent with the disclosed embodiments.For example, personalization database 110 may include one or more memorydevice(s) storing data and software instructions and one or moreprocessor(s) configured to use the data and execute the softwareinstructions to perform server-based functions and operations known tothose skilled in the art.

Personalization database 110 may further include server(s) that areconfigured to execute stored software instructions to perform operationsassociated with collecting, storing, and accessing profile data relatedto user 108, including one or more processes associated with gathering,for example, data related to user 108's demographics, accessibilityneeds, display preferences, and biometrics information. Personalizationdatabase 110 may gather the data from a variety of sources, compile thedata, and organize the data into easily accessible profiles.Personalization database 110 may include one or more servers that may bea general purpose computer, mainframe computer, or any combination ofthese components. In certain embodiments, Personalization database 110(or a system including personalization database 110) may be configuredas a particular apparatus, system, and the like based on the storage,execution, and/or implementation of the software instructions thatperform one or more operations consistent with the disclosedembodiments. A personalization database 110 may be standalone, or it maybe part of a subsystem, which may be part of a larger system. Forexample, personalization database 110 may represent distributed serversthat are remotely located and communicate over a network (e.g. network112) or a dedicated network, such as a LAN. An exemplary computer systemconsistent with personalization database 110 is discussed in additionaldetail with respect to FIG. 2.

In certain embodiments, personalization database 110 may be associatedwith an entity, such as a company, organization, agency, etc. In oneembodiment, the personalization database entity may be a differententity than a financial service provider associated with FSP device 102.In certain aspects, a user or user(s) affiliated with a personalizationdatabase entity may operate one or more components associated withpersonalization database 110 to collect and maintain personalizationdata. In other embodiments, personalization database 110 may beassociated with a financial service provider or other entity associatedwith FSP device 102. For example, personalization database 110 may be apart or subpart of FSP device 102.

Network 112 may comprise any type of computer networking arrangementused to exchange data. For example, network 112 may be the Internet, aprivate data network, a virtual private network using a public network,a WiFi network, a LAN or WAN network, and/or other suitable connectionsthat may enable information exchange among various components of thesystem 100. Network 112 may also include a public switched telephonenetwork (“PSTN”) and/or a wireless cellular network. Network 112 may bea secured network or unsecured network. In other embodiments, one ormore components of system 100 may communicate directly through adedicated communication link(s), such as links between user device 106,FSP device 102, local FSP device 104, and personalization database 110.

Additionally or alternatively, network 112 may include a directcommunication network. Direct communications may use any suitabletechnologies, including, for example, Bluetooth™, Bluetooth LE™ (BLE),WiFi, near field communications (NFC), or other suitable communicationmethods that provide a medium for transmitting data between separatedevices. In certain embodiments, user device 106 and local FSP device104 may connect and communicate through a direct communications network,for example, based on any of the above networking technologies.

Other components known to one of ordinary skill in the art may beincluded in system 100 to process, transmit, provide, and receiveinformation consistent with the disclosed embodiments.

FIG. 2 shows a diagram of an exemplary computing system 200 illustratinga computing system configuration that may be associated with FSP device102, local FSP device 104, user device 106, and/or personalizationdevice 110, consistent with disclosed embodiments. In one embodiment,computing system 200 may have one or more processors 210, one or morememories 230, and one or more input/output (I/O) devices 220. In someembodiments computing system 200 may take the form of a server, generalpurpose computer, a mainframe computer, laptop, smartphone, mobiledevice, or any combination of these components. In certain embodiments,computing system 200 (or a system including computing system 200) may beconfigured as a particular apparatus, system, and the like based on thestorage, execution, and/or implementation of the software instructionsthat perform one or more operations consistent with the disclosedembodiments. Computing system 200 may be standalone, or it may be partof a subsystem, which may be part of a larger system.

Processor 210 may include one or more known processing devices, such asa microprocessor from the Pentium™ or Xeon™ family manufactured byIntel™, the Turion™ family manufactured by AMD™, or any of variousprocessors manufactured by Sun Microsystems. Processor 210 mayconstitute a single core or multiple core processor that executesparallel processes simultaneously. For example, processor 210 may be asingle core processor configured with virtual processing technologies.In certain embodiments, processor 210 may use logical processors tosimultaneously execute and control multiple processes. Processor 210 mayimplement virtual machine technologies, or other known technologies toprovide the ability to execute, control, run, manipulate, store, etc.multiple software processes, applications, programs, etc. In anotherembodiment, processor 210 may include a multiple-core processorarrangement (e.g., dual, quad core, etc.) configured to provide parallelprocessing functionalities to allow computing system 200 to executemultiple processes simultaneously. One of ordinary skill in the artwould understand that other types of processor arrangements could beimplemented that provide for the capabilities disclosed herein. Thedisclosed embodiments are not limited to any type of processor(s)configured in computing system 200.

Memory 230 may include one or more storage devices configured to storeinstructions used by processor 210 to perform functions related to thedisclosed embodiments For example, memory 230 may be configured with oneor more software instructions, such as program(s) 236 that may performone or more operations when executed by processor 210. The disclosedembodiments are not limited to separate programs or computers configuredto perform dedicated tasks. For example, memory 230 may include aprogram 236 that performs the functions of computing system 200, orprogram 236 could comprise multiple programs. Additionally, processor210 may execute one or more programs located remotely from computingsystem 200. For example, FSP device 102, local FSP device 104, userdevice 106, or personalization database 110, may, via computing system200 (or variants thereof), access one or more remote programs that, whenexecuted, perform functions related to certain disclosed embodiments.Processor 210 may further execute one or more programs located indatabase 240. In some embodiments, programs 236 may be stored in anexternal storage device, such as a cloud server located outside ofcomputing system 200, and processor 210 may execute programs 236remotely.

Programs executed by processor 210 may cause processor 210 to executeone or more processes related to financial services provided to usersincluding, but not limited to, processing credit and debit cardtransactions, checking transactions, fund deposits and withdrawals,transferring money between financial accounts, lending loans, processingpayments for credit card and loan accounts, processing orders forcertified funds, processing orders for new or reissue debit cards, andprocessing ATM cash withdrawals.

Memory 230 may also store data that may reflect any type of informationin any format that the system may use to perform operations consistentwith the disclosed embodiments. Memory 230 may store instructions toenable processor 210 to execute one or more applications, such as serverapplications, network communication processes, and any other type ofapplication or software. Alternatively, the instructions, applicationprograms, etc., may be stored in an external storage (not shown) incommunication with computing system 200 via network 112 or any othersuitable network. Memory 230 may be a volatile or non-volatile,magnetic, semiconductor, tape, optical, removable, non-removable, orother type of storage device or tangible (i.e., non-transitory)computer-readable medium.

Memory 230 may include transaction data 232. Transaction data 232 mayinclude information related to financial transactions initiated by auser. For example, transaction data may include a user identifier and atransaction type. The user identifier may be a credit or debit cardnumber, and account number, or another means for identifying the userinitiating the financial transaction. The transaction type may includean indicator of the type of transaction the user is initiating, such as,ATM cash withdrawal, debit PIN reset, money wire or transfer, call tothe customer service center, ordering a new or reissue debit card,ordering certified funds, or other transactions requiring userauthentication. Transaction data 232 may also include authenticationdata obtained from the user for the purposes of authorizing thetransaction by verifying the authenticity of provided biometric data ascompared to stored biometric data. Additionally or alternatively,transaction data 232 may be stored in database 240 or in an externalstorage (not shown) in communication with computing system 200 vianetwork 112 or any other suitable network.

Memory 230 may further include customer data 234. Customer data 234 mayinclude information about particular customers of the financial serviceprovider. For example, customer data 234 ray include clients' accountinformation, debit or credit card information, history of purchasetransactions, financial statements, credit score, risk profile, usernameand password, debit card PIN, home and work locations, and/or biometricinformation. Additionally, customer data 234 may include user deviceidentification information, such as, for example, a phone number, emailaddress, IP address, Bluetooth signature, or other device identifier.Alternatively customer data 234 may be stored in database 240, or in anexternal storage (not shown) or in personalization database 110 incommunication with computing system 200 via network 112 or any othersuitable network.

Processor 210 r ay analyze transaction data 232 in reference to customerdata 234. For example, processor 210 may analyze transaction data todetermine which client with information stored in customer data 234 isinitiating the financial transaction. Processor 210 may access theparticular user's customer information to determine their accountinformation, debit or credit card information, history of purchasetransactions, financial statements, credit score, risk profile, usernameand password, debit card PIN, home and work locations, and/orauthentication data.

I/O devices 220 may be one or more device that is configured to allowdata to be received and/or transmitted by computing system 200. I/Odevices 220 may include one or more digital and/or analog communicationdevices that allow computing system 200 to communicate with othermachines and devices, such as other components of system 100 shown inFIG. 1. For example, computing system 200 may include interfacecomponents, which may provide interfaces to one or more input devices,such as one or snore keyboards, mouse devices, displays, touch sensors,card readers, biometric readers, cameras, scanners, microphones,wireless communications devices, and the like, which may enablecomputing system 200 to receive input from an operator of local FSPdevice 102, such as user 108.

Computing system 200 may also contain one or more database(s) 240.Alternatively, computing system 200 may be communicatively connected toone or more database(s) 240. Computing system 200 may be communicativelyconnected to database(s) 240 through network 112. Database 240 mayinclude one or more memory devices that store information and areaccessed and/or managed through computing system 200. By way of example,database(s) 240 may include Oracle™ databases, Sybase™ databases, orother relational databases or non-relational databases, such as Hadoopsequence files, HBase, or Cassandra. The databases or other files mayinclude, for example, data and information related to the source anddestination of a network request, the data contained in the request,etc. Systems and methods of disclosed embodiments, however, are notlimited to separate databases. Database 240 may include computingcomponents (e.g., database management system, database server, etc.)configured to receive and process requests for data stored in memorydevices of database(s) 240 and to provide data from database 240.

As discussed above, local FSP device 104 may include at least onecomputing system 200. Further, although sometimes discussed here inrelation to local FSP device 104, it should be understood thatvariations of computing system 200 may be used by other components ofsystem 100, including FSP device 102 user device 106, andpersonalization database 110. Computing system 200 may be a standalonedevice or server or may be configured as a distributed computer systemincluding multiple servers or computers that interoperate to perform oneor more of the processes and functionalities associated with thedisclosed embodiments.

FIG. 3 shows an exemplary ATM personalization process, consistent withdisclosed embodiments. Process 300 may be performed by processor 210 of,for example, local FSP device 104 executing instructions encoded on acomputer-readable medium storage device for providing ATM functionality.It is to be understood, however, that one or more steps of process 300may be implemented by other components of system 100 (shown or notshown), including, FSP device 102 and/or user device 108.

At step 302, local FSP device 104 may receive authentication data from auser. Authentication data may be identifying information such as anaccount number, personal identification number (PIN), social securitynumber, biometric information etc. As an example, user 108 may insert atransaction card such as a credit, debit, or ATM card into a card reader(not shown) connected to local FSP device 104 in order to identify user108's association with a financial service provider. FSP device 104 mayalso receive a fingerprint, iris scan, or voice sample provided to asensor in communication with local FSP device 104. Alternatively, FSPdevice 104 may receive authentication via a wired or wireless connectionwith user device 106.

FIG. 4 shows ATM 400, an example of an embodiment of local FSP device104. ATM 400 may include a touch-sensitive display 402. Display 402 maycomprise any size or form factor display based on any displaytechnology, such as LCD, CRT, plasma, OLED, etc. As an example, FIG. 4depicts display 402 as a 78″ diagonal OLED display. As shown in FIG. 4,display 402 may be oriented vertically such that the display is tallerthan it is wide. Display 402 may be mounted flush with a wall or othersurface or behind a glass barrier (not shown) such that unauthorizeddevices may be more difficult to attach to ATM 400 and/or more easilydetected.

As shown in FIG. 4, ATM 400 may display an interface via display 402,requesting authorization data from user 108. ATM 400 may display agraphical element such as a target 404, indicating a portion of display402, that is enabled to, or is in proximity to a device enabled toconnect to user device 106. User 108 may position user device 106 closeto target 404, initiating a wireless connection between user device 106and ATM 400, in which ATM 400 may receive user 108's authorization data.

Referring back to FIG. 3, at step 304, local FSP device 104 may retrieveuser profile 304. For example, local FSP device 104 may communicate withpersonalization database 110 and/or FSP device 102, over network 112, torequest user profile 304. Alternatively, user profile 304 may bereceived from user device 106.

At step 306, local FSP device 104 may determine interface attributesbased on the retrieved user profile. The determined attributes may varywidely, and may be based on any number of attributes or preferences ofuser 108. For example, FIG. 5 shows a side view cross section of display402. As shown in FIG. 5, display 402 may include a display panel 502behind a layer of glass 504 of a given thickness 506. Glass 504 may betouch sensitive based on, for example, capacitive sensing technology.Based on the retrieved user profile information, specificallyinformation related to the height of user 108, local FSP device 104 maydetermine that user 108 is likely to view an interface element displayedat location 508 of display 402 along line of sight 510. As a result, theinterface element may be visible to user 108 at location 514 of glass504. Accordingly, local FSP device 104 may determine that touch sensordata indicating an interaction at or near location 514 will beinterpreted as a selection of the interface element displayed atlocation 508.

Alternatively, the retrieved user profile information may indicate thatuser 108 is taller, and is likely to view an interface element displayedat location 508 of display 402 along line of sight 512. In this case,the interface element may be visible to user 108 at location 516 ofglass 504. Accordingly, local FSP device 104 may determine that touchsensor data indicating an interaction at or near location 516 will beinterpreted as a selection of the interface element displayed atlocation 508.

In an embodiment, local FSP device may be configured to arrangeinterface elements to be displayed on display 402 based on the retrieveduser profile information. For example, local FSP device 104 maydetermine, based on height information included in the user profileinformation, that the interface element will be displayed at location518 instead of location 508, such that when viewed along line of sight520, the interface element will be visible at location 522. Thus, theheight of interface elements of an ATM interface may be set in order todisplay the interface elements at “eye level” for user 108. Furtherexamples of this principle are shown in FIGS. 6A and 6B.

Referring back to FIG. 3, at step 308, local FSP device 104 may generatean ATM interface for display to user 108, based on the determinedinterface attributes.

FIGS. 6A and 6B show examples of interfaces that may displayed viadisplay 402 of ATM 400 and include attributes determined based on theuser profile. FIG. 6A shows an example of an interface that may begenerated based on user profile information associated with user 108that indicates user 108 is of above average height. As shown in FIG. 6A,ATM 400 may further determine a portion of display 402 to remain unused.For example, ATM 400 may generate an interface that occupies only aportion of display 402, based on the portion of the display likely to bewithin convenient reach and/or view based on user 108's user profileinformation. Alternatively, space outside user 108's reach or view maybe used to display a background image, such as a patterned wallpaper,the logo of the financial service provider associated with ATM 400, orthe like.

FIG. 6B shows an example of an interface that may be displayed based onuser profile information that indicates that user 108 is of belowaverage height, wherein the interface occupies a lower portion ofdisplay 402.

In some embodiments, display 402 may be disposed such that the lowestpossible height for display of an interface is at least withinspecifications set by regulations such as the Americans withDisabilities Act (ADA). Further, user profile information may includeinformation related to abilities or disabilities of user 108. Forexample, ATM 400 may determine that an ATM interface should be displayedat a height appropriate for an individual in a wheelchair based on userprofile information indicating that user 108 uses a wheelchair. Userprofile information may also include information related to visualability, hearing ability, or motor skills. Thus, ATM 400 may determinethat an ATM interface will display interface elements such as buttons,text, or images (as shown in FIG. 7A) of a particular size or contrast,or favor or avoid certain colors, patterns, or animations due to eyeconditions or colorblindness. As another example, user 108 may havedifficulty with touch based input devices, and thus have a tendency toselect multiple interface elements inadvertently. This tendency may beincluded in user 108's profile information, and ATM 400 may, as aresult, generate an ATM interface that ignores repeated inputs in ashort period of time. As a further example, user 108's profileinformation may include information indicating that user 108 has ahearing disability. Based on this information, ATM 400 may generate aninterface that includes amplified or adapted audio, favors visual cuesover audio, incorporates Telecommunications Devices for the Deaf (TTD)services, etc. Additionally or alternatively, user 108's profileinformation may include an indication that user 108 uses a hearingdevice such as a hearing aid or an implant such as those distributed byCochlear Ltd. ATM 400 may automatically pair with a Bluetooth or otherwireless audio feature included in such devices based on informationincluded in user profile information.

As shown in FIG. 7B, ATM 400 may also automatically display an interfacein user 108's preferred language based on received user profileinformation.

Retrieved user profile information may include information related toservices in which user 108 is enrolled. For example, user 108 may be anaccount holder of a financial account that accepts checks or otherwritten instruments for deposits and/or payments. Based on retrieveduser profile information, ATM 400 may request that user 108 present sucha payment instrument. The payment instrument may be accepted at ATM 400in a variety of ways such as via a slot or an image capture device(e.g., a scanner or camera), and instructions for presenting payment maybe adapted based on other aspects of user 108's user profileinformation.

As an example, as shown in FIGS. 8A and 8B, ATM 400 may display aninterface requesting presentation of a check for deposit into afinancial account. The interface may direct user 108 to the location ofthe slot, camera, scanner, etc. based on any of the attributes describedabove. For example, ATM 400 may accept deposits using a camera 802disposed in proximity with display 402. Camera 802 may captureinformation from a payment instrument necessary for completing paymentsand/or deposits. In some embodiments camera 802 may be disposed behind acommon transparent surface with display 402. Camera 802 may beidentified by a visual identifier, visible on the transparent surface inthe shape of a check, as shown in FIGS. 8A and 8B. ATM 400 may capturedata from a check placed against the transparent surface within theboundaries of the visual identifier. Based on user profile informationindicating that user 108 is of above average height, ATM 400 may displaythe interface shown in FIG. 8A, which directs user 108's attention downto camera 802. Alternatively, based on user profile informationindicating that user 108 is of below average height, ATM 400 may displaythe interface shown in FIG. 8B, which directs user 108's attention up tocamera 802. In some embodiments, ATM 400 may be configured to adjust thephysical location of camera 802, and any identifier corresponding tocamera 802, within ATM 400 based on the user profile information, andthe interface may direct user 108 to the adjusted physical location ofcamera 802. In some embodiments, camera 802 may be configured to capturepayment instrument information from anywhere within an area in front ofATM 400. In such embodiments, ATM 400 may display an interfacerequesting user 108 to display the payment instrument, at any location,such that the payment instrument faces ATM 400.

In some examples, some or all of the logic for the above-describedtechniques may be implemented as a computer program or application or asa plug in module or sub component of another application. The describedtechniques may be varied and are not limited to the examples ordescriptions provided. In some examples applications may be developedfor download to mobile communications and computing devices, e.g.,laptops, mobile computers, tablet computers, smart phones, etc., beingmade available for download by the user either directly from the deviceor through a website.

Moreover, while illustrative embodiments have been described herein, thescope thereof includes any and all embodiments having equivalentelements, modifications, omissions, combinations (e.g., of aspectsacross various embodiments), adaptations and/or alterations as would beappreciated by those in the art based on the present disclosure. Forexample, the number and orientation of components shown in the exemplarysystems may be modified. Further, with respect to the exemplary methodsillustrated in the attached drawings, the order and sequence of stepsmay be modified, and steps may be added or deleted.

Thus, the foregoing description has been presented for purposes ofillustration. It is not exhaustive and is not limiting to the preciseforms or embodiments disclosed. Modifications and adaptations will beapparent to those skilled in the art from consideration of thespecification and practice of the disclosed embodiments. For example,while a financial service provider has been described herein as theentity detecting and identifying customers, it is to be understood thatconsistent with disclosed embodiments another entity may provide suchservices in conjunction with or separate from a financial serviceprovider.

The claims are to be interpreted broadly based on the language employedin the claims and not limited to examples described in the presentspecification, which examples are to be construed as non-exclusive.Further, the steps of the disclosed methods may be modified in anymanner, including by reordering steps and/or inserting or deletingsteps.

Furthermore, although aspects of the disclosed embodiments are describedas being associated with data stored in memory and other tangiblecomputer-readable storage mediums, one skilled in the art willappreciate that these aspects can also be stored on and executed frommany types of tangible computer-readable media, such as secondarystorage devices, like hard disks, floppy disks, or CD-ROM, or otherforms of RAM or ROM. Accordingly, the disclosed embodiments are notlimited to the above described examples, but instead is defined by theappended claims in light of their full scope of equivalents.

1-20. (canceled)
 21. A system, comprising: a touch-sensitive display;one or more memory devices storing instructions; and or more processorsconfigured to execute the instructions to: receive, from a user device,authentication data comprising biometric data associated with a user;retrieve, over a network, user profile information based on thebiometric data, the user profile information indicating at least onephysical trait of the user, wherein the at least one physical trait ofthe user comprises an indication of a height of the user; determine userinterface attributes based on the user profile information, whereindetermining the user interface attributes includes: assigning touchinput locations on the touch-sensitive display based on the indicationof a height of the user and a thickness of the touch sensitive display,and identifying, with a biometric camera, an eye level for the userbased on the retrieved user height; and generate an automatic tellermachine interface on the touch-sensitive display based on the userprofile information and based on the identified user eye level.
 22. Thesystem of claim 21, wherein determining user interface attributesincludes assigning a language of the user interface based on the userprofile information.
 23. The system of claim 21, wherein determininguser interface attributes includes determining a portion of thetouch-sensitive display that will be unused by the automatic tellermachine interface.
 24. The system of claim 23, wherein the unusedportion of the touch-sensitive display is determined based on a portionof the display outside one or more of the user's reach or view, based onthe user profile information.
 25. The system of claim 21, whereindetermining user interface attributes includes assigning at least one oftext size, interface element size, or interface element color, based onthe user profile information.
 26. The system of claim 21, wherein thesystem further includes an image capture device; and wherein the one ormore processors are further configured to direct the user to present apayment instrument to the image capture device, based on the userprofile information.
 27. The system of claim 21, wherein the at leastone physical trait of the user further comprises an indication of avisual impairment of the user; and determining user interface attributesincludes assigning, at least one of text size, interface element size,or interface element color, based on the indication of a visualimpairment of the user.
 28. The system of claim 21, wherein the at leastone physical trait of the user further comprises an indication of adifficulty of the user in using touch-sensitive display, and determininguser interface attribute includes ignoring repeated inputs by the userwithin a predetermined period of time.
 29. A method for displaying anautomatic teller machine interface, the method comprising the followingoperations performed by one or more processors: receive, from a userdevice, authentication data comprising biometric data associated with auser; retrieve, over a network, user profile information based on thebiometric data, the user profile information indicating at least onephysical trait of the user, wherein the at least one physical trait ofthe user comprises an indication of a height of the user; determine userinterface attributes based on the user profile information, whereindetermining the user interface attributes includes: assigning touchinput locations on a touch-sensitive display based on the indication ofa height of the user and a thickness of the touch sensitive display, andidentifying, with a biometric camera, an eye level for the user based onthe retrieved user height; and generate an automatic teller machineinterface on the touch-sensitive display based on the user profileinformation and based on the identified user eye level.
 30. The methodof claim 29, wherein determining user interface attributes includesassigning a language of the user interface based on the user profileinformation.
 31. The method of claim 29, wherein determining userinterface attributes includes determining a portion of thetouch-sensitive display that will be unused by the automatic tellermachine interface.
 32. The method of claim 31, wherein the unusedportion of the touch-sensitive display is determined based on a portionof the display outside one or more of the user's reach or view, based onthe user profile information.
 33. The method of claim 29, whereindetermining user interface attributes includes assigning at least one oftext size, interface element size, or interface element color, based onthe user profile information.
 34. The method of claim 29, wherein theautomatic teller machine interface is configured to direct the user topresent a payment instrument to an image capture device, based on theuser profile information.
 35. The method of claim 29, wherein the atleast one physical trait of the user further comprises an indication ofa visual impairment of the user, and determining user interfaceattributes includes assigning at least one of text size, interfaceelement size, or interface element color, based on the indication of avisual impairment of the user.
 36. The method of claim 29, wherein theat least one physical trait of the user further comprises an indicationof a difficulty of the user in using touch-sensitive display, anddetermining user interface attribute includes ignoring repeated inputsby the user within a predetermined period of time.
 37. A systemcomprising: a touch-sensitive display; one or afore memory devicesstoring instructions; and one or more processors configured to executethe instructions to: receive, from a user device, authentication datacomprising biometric data associated with a user; retrieve, over anetwork, user profile information based on the biometric data, the userprofile information indicating at least one physical trait of the user,wherein the at least one physical trait of the user comprises anindication of a height of the user; determine user interface attributesbased on the user profile information, wherein determining the userinterface attributes includes assigning touch input locations on thetouch-sensitive display based on the indication of a height of the userand a thickness of the touch sensitive display; and generate anautomatic teller machine interface on the touch-sensitive display basedon the user profile information.